Scroll Bridge

Scroll TVL … Scroll …

Move assets to Scroll safely

Scroll Bridge is the canonical Ethereum–Scroll route: connect your wallet, review the transfer, sign it yourself, and track finalization.

Open the Scroll Bridge How it works

Preview

Preview only
Ethereum tokenEthereum 0.00Preview
Scroll tokenScroll 0.00Preview
Deposit · Ethereum → ScrollNon-custodial bridge route
Scroll token Scroll
TypeBridge route
CustodyNon-custodial
Go to Swap
Scroll

Bridge Scroll Protocol Architecture & Route Overview

Scroll’s canonical bridge is the protocol route between Ethereum Mainnet and Scroll Mainnet, using gateway and messenger contracts rather than a pooled liquidity network.

Open the App
Read more

In practice you connect a self-custody wallet, choose asset, amount and recipient, approve only when required, then sign the bridge transaction yourself; this page is an independent dashboard for reviewing that route before you authorize it. For mechanism detail, start with Scroll’s L1 and L2 bridging docs.

Routesource chain <-> destination chain
Deposittypically minutes
Withdrawmay need proving/finalization
Gasnative asset on both chains
CustodyNon-custodial — your wallet signs
VerifyUse the official contracts; beware fake bridge sites
Scroll Bridge

What is Bridge Scroll?
Scroll Bridge is Scroll’s canonical Ethereum↔Scroll bridge, not a third-party liquidity router. Deposits lock ETH or ERC-20 assets in Ethereum gateway contracts and release or represent the corresponding asset on Scroll; withdrawals send a cross-domain message back to Ethereum and complete only after rollup finalization and an L1 execution transaction. Unlike intent-based or liquidity bridges, this route does not add a counterparty or filler layer, although those routes may quote faster multi-chain transfers. Scroll’s model depends on its zkEVM proof system and finalized state; Ethereum’s bridge overview explains the cross-chain model.

How bridging works
Bridging works by approving if needed, signing the route, waiting for inclusion, and checking the destination balance. For ETH and ERC-20 transfers, the wallet interacts with gateway/router contracts; ERC-721, ERC-1155 and arbitrary messages use separate protocol gateways. The ERC-20 token standard defines the transfer and approval interface used by fungible token contracts. A route review should show the source network, destination network, token contract, recipient, approval scope, and contract route being signed.

Depositing to the destination
Depositing moves funds from Ethereum Mainnet to Scroll Mainnet; wait for Ethereum confirmation and Scroll inclusion before treating the balance as available. Keep ETH on Ethereum for the approval and deposit transaction, and keep ETH on Scroll for anything you want to do immediately after arrival. Scroll Mainnet chain ID is 534352 and Scroll Sepolia is 534351; the Scroll network record lists 534352 for the mainnet. If your wallet is on the wrong chain, the interface may still render while the transaction route is not the one you intended.

Withdrawing back
Withdrawing is a two-stage exit: submit on Scroll, then execute the Ethereum release after the batch is finalized with a validity proof. The withdrawal message enters Scroll’s withdrawal tree, and the L1 claim is a separate Ethereum transaction using a Merkle proof; do not submit duplicate withdrawals while the first is pending. If you may need the funds back on Ethereum quickly, size the bridge amount accordingly instead of bridging everything and discovering the exit clock later.

Time and fees
Time follows confirmation, inclusion, and—on withdrawals—rollup finalization; fees follow gas on the chain where you transact plus the final Ethereum execution cost for withdrawals. A deposit can require an ERC-20 approval and the deposit transaction on Ethereum; Scroll-side activity uses ETH as gas; a withdrawal adds Scroll gas first and Ethereum gas later for the claim. This Ethereum gas model is why one bridge action can contain separate fee-bearing transactions. Third-party routes can add provider or liquidity fees, so compare the full route rather than a headline quote.

Is Scroll Bridge safe?
Scroll Bridge is a canonical protocol route, but an audit or open-source code does not remove execution risk. The relevant failure points are contract defects, upgrade/admin or emergency-pause controls, compromised interfaces, network disruption, approval abuse, phishing clones, and search-ad lookalikes; bridged L1 assets are also held by escrow or messenger contracts while the route completes. Verify the domain, chain ID, token, recipient, approval scope, and contract route, and treat every signature as spend authority. A request for a seed phrase, an unexplained unlimited approval, or an untraceable contract is outside the bridge flow; compare the route with L2BEAT’s Scroll profile before authorizing.

Problems and fixes
Most bridge problems come from the wrong network, missing destination gas, or a pending finalization window. If the wallet shows Ethereum when you meant Scroll, switch chains before signing; if funds arrived but you cannot transact, add ETH on Scroll; if a withdrawal is “stuck,” check whether it is waiting for rollup finalization and the separate L1 claim.

Verified Contract Gateway: 0x8453000000000000000000000000000000000000 (Chain verification active)

Scroll FAQ
Is this the official Scroll Bridge site?

No. This is an independent, non-custodial informational dashboard for reviewing routes, costs, timing and risks before you authorize a transaction from your own wallet.

How long does bridging to Scroll take?

Deposits are limited by Ethereum confirmation plus Scroll inclusion; withdrawals also need rollup finalization and a separate Ethereum execution transaction.

How do I bridge to Scroll?

Connect a self-custody wallet, select Ethereum Mainnet to Scroll Mainnet, choose the asset, amount and recipient, review the route, approve the token only if required, then sign the bridge transaction; the wallet prompt is the final authorization step.

Do I need ETH on Scroll before bridging?

For a simple deposit you mainly need ETH on Ethereum to send the transaction, but you will want ETH on Scroll to swap, transfer or interact after arrival because ETH is Scroll’s native gas currency.

Is the Scroll Bridge safe to use?

A canonical route still requires the contract, interface, approval, and signature checks listed in Is Scroll Bridge safe?

Should I use the native bridge or a third-party bridge?

Choose the native bridge for Scroll’s native messaging and finalized rollup state; choose a third-party route when flexibility is worth its provider, liquidity, or filler layer. The trade is simplicity and native finality versus route flexibility.

Notes before you use Scroll Bridge

Before you sign, check the bridge site, token, recipient, contract route, and network: Ethereum Mainnet 1 to Scroll Mainnet 534352, not Sepolia 534351 unless you are testing; keep ETH available on both chains, and remember that withdrawals need finalization plus a later Ethereum claim. Verification habit: I re-check the domain, chain ID and contract route every session rather than trusting bookmarks; last reviewed 21 July 2026. Independent reference — confirm the route in your own wallet.